| |
|
| |
This article contains an overview of LDAP components and how IBM Sametime Community Server works with LDAP to provide authentication, name lookups, and name resolution. The article describes best practices for creating search filters, setting sametime.ini parameters, and enhancing Sametime and ... |
| |
|
| |
In this section, we discuss some strategies and items to check for the network. ==Introduction==
The network plays a key part in the performance of the STResolve service. The key areas to investigate are on, and also between, the Sametime Server and LDAP server. Certain operating systems have ... |
| |
|
| |
In this section, we describe best practices for LDAP optimizations. Each LDAP implementation is unique, so it is not possible to give an exact set of steps for changes on the directory server. However, there are a few best practices that apply globally to all LDAP implementations, as follows: ... |
| |
|
| |
This section describes clientside best practices to ensure quick, effective, optimized name lookup searches. Introduction
The Sametime Connect client (standalone) and Lotus Notes client are the main generators of name lookup requests. As well, certain server applications such as the Sametime ... |
| |
|
| |
recommendations and best practices for configuring your Lotus Sametime server for best Name Lookup (also called STResolve) performance |
| |
|
| |
This guide provides a high-level overview, background information, and best practice recommendations on Lotus Sametime's Name Lookup solution. ==Introduction==
One of the most heavily used features of the Lotus Sametime server is the Sametime Resolve (STResolve) service that provides name lookup ... |